Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add retries to schema sync #29

Merged
merged 1 commit into from
May 26, 2021
Merged

Conversation

michaelklishin
Copy link
Member

So, do what RabbitMQ core does as of 3.6.7 or so.

This makes it possible for nodes with those plugins enabled to be
restarted in arbitrary order within a certain time window, just
like nodes without those plugins.

Closes #28

So, do what RabbitMQ core does as of 3.6.7 or so.

This makes it possible for nodes with those plugins enabled to be
restarted in arbitrary order within a certain time window, just
like nodes without those plugins.

Closes #28
@michaelklishin michaelklishin merged commit f76fd7f into master May 26, 2021
@michaelklishin michaelklishin deleted the mk-retry-schema-table-sync branch May 26, 2021 21:06
michaelklishin added a commit that referenced this pull request May 26, 2021
Add retries to schema sync

(cherry picked from commit f76fd7f)
@michaelklishin
Copy link
Member Author

Backported to v3.8.x.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Retry waiting for schema database tables the same way RabbitMQ core does
1 participant